SET PATH=C:\PRG\BO\PGM;C:\OS2;C:\CMD;C:\MUGLIB;C:\SQLLIB;C:\CMLIB;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\PRG\BO\PGM;C:\PRG\WORD;C:\PRG\EXCEL2;C:\DELIVERY;C:\PRG\OS2TOOL;C:\COSY\PGM;C:\NETWARE;
SET DPATH=C:\OS2;C:\MUGLIB\DLL;C:\CMLIB;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\NETWARE;C:\PRG\OS2TOOL;
REM The following line makes the OS/2 Command Prompt "blue", in addition to
REM the DOS-Box Command Prompt being "red" as a visual aid to distinguish the
REM DOS-Box from a full-screen OS/2 Command Prompt.
SET PROMPT=$i$E[1;36m$P $E[0m
SET HELP=C:\OS2\HELP;
SET BOOKSHELF=C:\OS2\BOOK;C:\PRG\BO\BOOK;
BUFFERS=60
IOPL=YES
SET TMP=C:\TMP
SET TEMP=C:\TMP
REM In the following line, for a machine with many Megabytes of memory,
REM you might consider increasing the DISKCACHE !
DISKCACHE=512
rem DISKCACHE=1024
REM In case you do not want a machine to stop at boot time when discovering
REM errors or problems in CONFIG.SYS, you may activate the following line
rem PAUSEONERROR=NO
MAXWAIT=3
MEMMAN=SWAP,MOVE,SWAPDOS
PROTECTONLY=NO
REM The following line reserves a minimum of 4 Megabyte as Swap-Space
REM on the harddisk.
SWAPPATH=C:\OS2\SYSTEM 4096
THREADS=512
SHELL=C:\OS2\COMMAND.COM /P /E:1024
BREAK=ON
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\DOS.SYS
REM In the following two lines, the standard Keyboard Layout and
REM Country Information is set to be German. This has to be set
REM according to the Country desired. COUNTRY needs to be re-applied
REM also in the PM Control Panel (PMCPL.EXE) in order to be written
REM into each workstations OS2.INI file.
COUNTRY=049,C:\OS2\SYSTEM\COUNTRY.SYS
DEVINFO=KBD,GR,C:\OS2\KEYBOARD.DCP
REM Very important: in order to successfully install and run certain
REM MSS Applications such as COSY, the primary CODEPAGE used is 850 !!
REM For DOS-Compatibility Box utilities, the CODEPAGE is changed to
REM "437" (including linedraw characters) in AUTOEXEC.BAT.
CODEPAGE=850,437
REM The following lines apply to VGA-monitors. If using higher resolution
REM display adapters such as the IBM 8514/A or XGA, you must change these
REM lines accordingly and also copy the appropriate DLL (e.g. IBMBGA.DLL
REM for 8514/A support or the IBMXGA.DLL for XGA support) off the \OS2\DLL
REM directory to the filename C:\OS2\DLL\DISPLAY.DLL (under DOS).
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_IBMVGA
SET VIO_IBMVGA=DEVICE(BVHVGA)
REM When running an IBM 8514/A Adapter, the above three lines
REM need to be changed to the following three lines for 8514-Support.
REM Remember to set the STARTLW.DLL into to OS2.INI file as a SYSDLL
REM entry under LoadOneTime.
rem DEVINFO=SCR,BGA,C:\OS2\VIOTBL.DCP
rem SET VIDEO_DEVICES=VIO_IBM8514A
rem SET VIO_IBM8514A=DEVICE(BVHVGA,BVH8514A)
REM When running an XGA Graphics Adapter from IBM, the following
REM four (!) lines apply to XGA Support. The DEVINFO Line needs to
REM be set to the appropriate monitor being used, in this case VGA!
rem DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
rem SET VIDEO_DEVICES=VIO_IBMXWY
rem SET VIO_IBMXWY=DEVICE(BHVVGA,BHVXGA)
rem DEVICE=C:\OS2\XGARING0.SYS
DEVICE=C:\OS2\POINTDD.SYS
REM The following two lines apply to IBM PS/2 Mouse. When running another
REM mouse on the system, you might have to change these two lines, see
REM example for a Microsoft PS/2 Bus Mouse.
rem DEVICE=C:\OS2\MSPS202.SYS
rem DEVICE=C:\OS2\MOUSE.SYS TYPE=MSPS2$
DEVICE=C:\OS2\IBMMOU02.SYS
DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$
DEVICE=C:\OS2\PMDD.SYS
DEVICE=C:\OS2\EGA.SYS
DEVICE=C:\OS2\ANSI.SYS
SET KEYS=ON
REM The following line activates support for RS 232, i.e. for modems.
REM The COM02.SYS driver is capable of supporting COM1 to COM3.
rem DEVICE=C:\OS2\COM02.SYS
REM ****************** CHI Corporation UNISYS **********************
REM In order to activate the gateway, remove the rem from the
REM DEVICE= Statement and rename C:\STARTUP. to C:\STARTUP.CMD
REM in order to start the CHI Gateway at boot time.
REM
REM Please make shure that the CHI-Board run on a higher Interrupt
REM Request Level than the Token Ring Card, i.e. IRQ 9 for CHI and
REM IRQ 10 or 3 for Token Ring, which is lower. This seems to provide
REM better results especially on slow gateway machines.
REM
REM Remember: IRQ Priorities run as follows (from highest to lowest):
REM 2, 9, 10, 11, 12, 13, 14, 15, 3, 4, 5, 6, 7.
REM
REM You should have a version level of at least 7.83 of the CHI OS/2
REM software installed in your system. This gateway also allows
REM DOS Clients to connect to UNISYS using DOSNP.EXE before loading
REM NETx.COM and after loading IPX.COM (and ROUTE.COM for Source
REM Routing in an IBM Bridge environment).
REM
rem DEVICE=C:\PRG\CHI\GW\UNISCOPE.SYS
REM *********** END of CHI Corporation UNISYS SPECIFICS ************
REM **************** IBM COMMUNICATIONS MANAGER **********************
REM Usage of the IBM Token Ring Adapter requires certain settings
REM such as Token Ring ROM Address range as well as SHARED RAM
REM Address range. You should be using only the newer 16/4 Adapter.
REM Settings of the addresses is done through the "Reference-Disk"
REM on any Microchannel machine such as IBM PS/2.
REM
REM There are recommendations and requirements concerning the size
REM of the SHARED RAM on the Token Ring card:
REM
REM GATEWAYS should be configured with 64 KB shared RAM,
REM plus have their SDLC, X.25 or Modem card such as CHI
REM configured to run on a higher IRQ than the Token Ring
REM card if possible.
REM
REM SDLC Gateways should set the Token IRQ to 10 if possible.
REM X.25 Gateways should set the Dual Ported RAM Window to
REM a size of at least 64 KB.
REM
REM WORKSTATIONS should be configured with at least 32 KB shared RAM.
REM If using an old 4 MBit Token Ring Adapter, this will not be possible.
REM Therefore you will not be able to run certain protocols, such as
REM multiple LU 6.2 sessions. In addition, you will have problems in
REM accomodating LSL buffers for the Novell NetWare Requester, which
REM depends on the Transmit Buffer Size (when using the newer
REM CMGRLAN.SYS + ROUTE.SYS) set in the active CFG-Configuration File
REM of Communications Manager. Transmit Buffer Size in CM's LAN Profile
REM for IEEE 802.2 should be set to a minimum of at least 1136 Bytes.
REM Standard Configuration is at least 1944 Bytes.
REM
REM The following driver is necessary always to provide Ring 0
REM Communications Services.
DEVICE=C:\CMLIB\R0CSDD.SYS
REM The following two lines are necessary to activate CM X.25 Support!!
REM This applies to gateway machines only, on which the board resides !!
REM If you don't find the program ICAAIM.COM in CMLIB, look for it on
REM the X.25 Coprocessor Board's Disk.
rem DEVICE=C:\CMLIB\ICARICIO.SYS
rem RUN=C:\CMLIB\ICALDRIC.EXE 0 C:\CMLIB\ICAAIM.COM 0
REM The following line is for SDLC Support such as the IBM Multi
REM Protocol Adapter (MPA), this applies to machines only, on which
REM the SDLC board resides. "S" means sharing of the interrupt.
rem DEVICE=C:\CMLIB\SDLCDD.SYS S 0
DEVICE=C:\CMLIB\LANDD.SYS
REM In the following line, you have to change the CFG filename
REM according to the function of the machine, i.e. SDLCGW !!
DEVICE=C:\CMLIB\TRNETDD.SYS CFG=C:\CMLIB\IWS.CFG
RUN=C:\CMLIB\ACSTRSYS.EXE
REM The following line is for support of IBM CM Asynchronous Mode.
rem DEVICE=C:\CMLIB\ASYNCDDB.SYS
REM The following line is for DFT terminal-definitions.
rem DEVICE=C:\CMLIB\DFTDD.SYS
REM The following line is for NETBIOS support !
REM So far, we don't know yet any application used by DLH really
REM requiring NETBIOS support. Packages such as LDU (LAN Download
REM Utility) from IBM, however, do need IBM NetBios.
REM Again, do not forget to change the CFG filename.
rem DEVICE=C:\CMLIB\NETBDD.SYS CFG=C:\CMLIB\IWS.CFG
REM The following line is for Remote Database Services.
DEVICE=C:\CMLIB\RDSLANDD.SYS
REM ********** END of IBM COMMUNICATIONS MANAGER SPECIFICS *********
REM ******************* IBM DATABASE MANAGER **********************
LOG=ON
SET QRWDR=C:
SET QRWINST=C:\SQLLIB
REM ************ END of IBM DATABASE MANAGER SPEFICICS *************
REM ***************** FRA AV3 BO Version 1.03.04 *******************
REM BO Version 1.03.04 must AUTOSTART the IBM Communications Manager
REM when the machine is configured for BO Remote Database Services.
REM Activate then the following line with the appropriate name of the
REM configured BO Database Server (see ADMDOC BO Reference Book).
REM BO Version 1.4 will have other configuration options to start
REM Remote Data Services and Communications Manager.
rem SET BONODE=???
REM ********** END of FRA AV3 BO Version 1.03.04 SPECIFICS *********
REM *************** NOVELL NetWare OS/2 Requester ******************
REM Attention: Further NOVELL NetWare OS/2 Requester parameters
REM can be configured in C:\NET.CFG.
REM
REM Current level of the Novell NetWare Requester for OS/2 as of
REM July 19th, 1991 is 1.3 plus NSD 2. Latest file date is 28.6.1991.
REM
REM Standard settings in NET.CFG contain parameters for named pipes
REM support particularly, for further details see the manual for the
REM Novell NetWare Requester for OS/2 Version 1.3, which provides
REM NetWare support for OS/2 all versions from 1.2 to 1.3.
REM
REM Remember: The Novell NetWare Requester for OS/2 is implemented
REM according to Novell's Open Datalink Interface specifications
REM (ODI), so that the requester can load multiple protocols such
REM as IPX, SPX, TCP/IP and other protocol stacks.
REM --- NetWare Requester statements BEGIN ---
REM The Link Support Layer is required before any LAN driver is loaded.
DEVICE=C:\NETWARE\LSL.SYS
REM The following DDAEMON is necessary to provide communication
REM between ????????.SYS drivers, which can't do Video-IO, and the
REM NetWare ??DAEMON.EXE daemons, which may then display any
REM Video Information necessary, i.e. error messages.
RUN=C:\NETWARE\DDAEMON.EXE
REM The LAN driver must match the board installed in the workstation.
REM The following two lines are to be used when running on Token Ring
REM WITHOUT ANY reference to IBM Communications Manager (C:\CMLIB)
REM in CONFIG.SYS. If using TOKEN.SYS, ROUTE.SYS must immediately
REM follow for source routing support.
rem DEVICE=C:\NETWARE\TOKEN.SYS
rem DEVICE=C:\NETWARE\ROUTE.SYS
REM The following line is used when running on Token Ring WITH
REM the IBM Communications Manager being activated in CONFIG.SYS.
REM Support for source routing is provided either by the parameter,
REM which indicated in this case that the Primary Token Ring Adapter
REM shall run with source routing enabled, or through the ROUTE.SYS.
REM As of July 1991, after Novell's Release of the NSD 2 for OS/2 1.3,
REM you may also use the new driver CMGRLAN.SYS plus ROUTE.SYS when
REM running with Communications Manager. You might need to adjust
REM the Link Support Buffer Size in NET.CFG according to the
REM Transmit Buffer Size set in the CM profile, i.e. IWS.CFG.
REM If you are running IBM TCP/IP for OS/2, you MUST use TOKENEE.SYS.
DEVICE=C:\NETWARE\TOKENEE.SYS 1=SOURCE
rem DEVICE=C:\NETWARE\CMGRLAN.SYS
rem DEVICE=C:\NETWARE\ROUTE.SYS
REM IPX must be loaded next after the LAN driver.
DEVICE=C:\NETWARE\IPX.SYS
REM SPX support is optional. Must be loaded before Named Pipes,
REM usage of NetWare printing utilities such as PCONSOLE.EXE
REM or Mailslots. All newer NetWare OS/2 utilities will require
REM to have SPX loaded.
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
REM The following line is for Named Pipe support, and must be followed
REM for the named pipe CLIENT side by the NPDAEMON line with no
REM parameter for COMPUTERNAME.
DEVICE=C:\NETWARE\NMPIPE.SYS
REM To activate a named pipe SERVER, remove the rem from the
REM NPSERVER.SYS line and give the machine a named pipe server name !
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE COMPUTERNAME
RUN=C:\NETWARE\NPDAEMON.EXE
REM The Requester driver must be loaded after IPX, SPX and Named Pipes.
DEVICE=C:\NETWARE\NWREQ.SYS
REM The NetWare Installable File System must be loaded after the
REM Requester driver.
IFS=C:\NETWARE\NWIFS.IFS
REM The NetWare daemon must be loaded after the Requester driver.
REM It should be left out (REM) when running purely in a
REM Non-File-Server-Environment as a named pipe server only,
REM i.e. when running as a UNISYS gateway with no Novell File-Server
REM in the same Internet. When bringing in a Novell Fileerver in such
REM a LAN, don't forget to again activate this line.
RUN=C:\NETWARE\NWDAEMON.EXE
REM The following two lines activate Novell's NETBIOS support !
REM They are optional, preference should be given to IBM's NETBIOS
REM support (through Communications Manager) if that is required.
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
REM Mailslots Support is optional. Must have SPX loaded before these line.
REM Mailslots are presently not supported under OS/2 1.30.1.
rem RUN=C:\NETWARE\MSDAEMON.EXE MS_COMPUTERNAME
REM NetWare Print Spooler Support is optional. Use it only if you want
